-
Notifications
You must be signed in to change notification settings - Fork 545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rbd: pre-work for VolumeGroup support #4701
Conversation
In the future we'll introduce a more standard interface for objects like Volumes and Snapshots. It is useful to have the context passed as 1st argument to all functions of those objects, including their Destroy() function. Signed-off-by: Niels de Vos <ndevos@ibm.com>
Signed-off-by: Niels de Vos <ndevos@ibm.com>
Renaming the `Delete()` function makes it easier to implement the upcoming `Volume` interface. Signed-off-by: Niels de Vos <ndevos@ibm.com>
1512a59
to
398cefd
Compare
The Volume interface will make it easier to work with the rbdImage struct, as the functions are cleaner defined. This benefits work that is needed for VolumeGroups and other CSI-Addons procedures. Signed-off-by: Niels de Vos <ndevos@ibm.com>
@Mergifyio queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 902946e |
/test ci/centos/k8s-e2e-external-storage/1.29 |
/test ci/centos/k8s-e2e-external-storage/1.28 |
/test ci/centos/k8s-e2e-external-storage/1.30 |
/test ci/centos/upgrade-tests-cephfs |
/test ci/centos/mini-e2e-helm/k8s-1.29 |
/test ci/centos/mini-e2e-helm/k8s-1.28 |
/test ci/centos/mini-e2e-helm/k8s-1.30 |
/test ci/centos/mini-e2e/k8s-1.28 |
/test ci/centos/mini-e2e/k8s-1.29 |
/test ci/centos/upgrade-tests-rbd |
/test ci/centos/k8s-e2e-external-storage/1.27 |
/test ci/centos/mini-e2e/k8s-1.30 |
/test ci/centos/mini-e2e-helm/k8s-1.27 |
/test ci/centos/mini-e2e/k8s-1.27 |
Describe what this PR does
Start defining a clean interface so that it will be easier to use the rbdImage/rbdVolume structs and their functions. The upcoming VolumeGroup interface will follow a similar principle, hopefully resulting in easier to maintain code.
Is there anything that requires special attention
The Volume interface is not used yet, in the future there will be a Manager interface that offers simple access to Volume and VolumeGroup objects. The Volume interface is not meant to be complete yet, it will get extended when there is a need for it (or when more cleanups are done).
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>
: retest the<job-name>
after unrelatedfailure (please report the failure too!)